MAINT: remove jax, pyro, torch, and gpu related software installs + GPU admonition #453
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@jstac this PR is adding a general https://6822f27dd8e5c4e161464ee6--nostalgic-wright-5fa355.netlify.app/ar1_bayes.html I have also shuffled a few installs around so that GPU related installs are separate to general packages. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses #452
This PR currently breaks🤔collabtesting. While googlecollabhasjaxit doesn't have a few other packages related to GPU such aspyrowhich is causing 1-2 lectures to fail. The installs will be listed at the top of the lecture, however a user will need to run that cell to install those packages for it to work.I have switched these back on for local execution (this should fix
collabwhile not upgrading the software for the other actions). I have documented this complexity and issue in #454 so doesn't need to be fixed here.